Hi @nathan-dovire ,

Thank you for your contribution to the AWS Amplify Flutter Library! Is there a reason this Pull Request is still a draft?

Hi @cadivus,
I’ve been testing this and noticed an issue with authentication when using the endpoint. Even after configuring the userPoolEndpoint, authentication still fails.

For context, in my use case authentication is handled via a custom auth endpoint that wraps the Cognito client. This Cognito client is protected by a client secret that is only available at runtime. The flow is:

• A request is made to the custom auth endpoint.
• That endpoint injects the Cognito client secret (provided at runtime).
• The endpoint then redirects the request directly to the Cognito authentication endpoint.

With this setup, simply adding userPoolEndpoint to the configuration does not seem to be sufficient. The auth request directly hits the Cognito endpoint and fails to authenticate, which suggests the current implementation may not fully support Cognito flows where the authentication request is executed directly against Cognito rather than through the custom endpoint.

Importantly, this flow works as expected when testing against v1.8.*. However, after upgrading to v2.x and above, authentication breaks with the same configuration, which strongly suggests a regression introduced in v2+.

Please let me know if this behavior is expected, or if there’s additional configuration or a recommended integration pattern for this scenario. I’m happy to help investigate further or contribute a fix once the intended behavior is clear.

Thanks!

Hi @nathan-dovire ,
we just merged #6477 which is similar to your PR. How exactly and where are you configuring your Cognito endpoint?

The merged PR worked for us by setting the userPoolEndpoint like this directly in amplify_outputs.dart: